Skip to content
This repository was archived by the owner on Nov 28, 2025. It is now read-only.

Move Lazer documentation to Pro section and remove lazer folder#927

Merged
aditya520 merged 1 commit intomainfrom
devin/1761672971-move-lazer-docs-to-pro
Oct 28, 2025
Merged

Move Lazer documentation to Pro section and remove lazer folder#927
aditya520 merged 1 commit intomainfrom
devin/1761672971-move-lazer-docs-to-pro

Conversation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot commented Oct 28, 2025

Description

This PR migrates the detailed Pyth Lazer technical documentation to the Pyth Pro section, completing the product rebrand. The placeholder content at /price-feeds/pro/how-lazer-works has been replaced with the comprehensive technical documentation that was previously located in the /lazer folder.

Changes made:

  • Replaced placeholder content in /pages/price-feeds/pro/how-lazer-works.mdx with detailed technical documentation covering the 5-tier architecture (Publishers, Relayers, Message Queue, Routers, History Service)
  • Updated all product name references from "Pyth Lazer" to "Pyth Pro" throughout the content
  • Removed the legacy /pages/lazer/ folder after content migration
  • Existing redirects in next.config.js will continue to handle legacy /lazer/* URLs

Type of Change

  • New Page
  • Page update/improvement
  • Fix typo/grammar
  • Restructure/reorganize content
  • Update links/references
  • Other (please describe):

Areas Affected

  • /pages/price-feeds/pro/how-lazer-works.mdx - Content replaced with full technical documentation
  • /pages/lazer/ folder - Removed after migration

Checklist

  • I ran npm run lint to check for linting errors (passed with pre-existing warnings only)
  • I have reviewed my changes for clarity and accuracy
  • All links are valid and working (requires human verification)
  • Images (if any) are properly formatted and include alt text (N/A)
  • Code examples (if any) are complete and functional
  • Content follows the established style guide
  • Changes are properly formatted in Markdown
  • Preview renders correctly in development environment (requires human verification)

Related Issues

N/A

Additional Notes

Important for reviewers:

  1. Test redirect functionality: Verify that /lazer/how-lazer-works properly redirects to /price-feeds/pro/how-lazer-works (redirects defined in next.config.js lines 127-128)
  2. Verify rebrand accuracy: Spot-check that "Lazer" → "Pro" replacements make sense in context, particularly in the technical descriptions
  3. Check navigation: Confirm the page appears correctly in the Pro section sidebar and that the legacy folder removal doesn't break any navigation elements
  4. Test internal links: Other pages reference /lazer paths - verify these are properly redirected (examples found in subscribe-price-updates.mdx and integration guides)

Redirect coverage: This PR relies on existing redirects in next.config.js. The following redirect rules should handle legacy URLs:

["/lazer", "/price-feeds/pro"],
["/lazer/:path*", "/price-feeds/pro/:path*"],

Contributor Information

Screenshots

N/A - Content migration only

@devin-ai-integration
Move Lazer documentation to Pro section and remove lazer folder
3087d7d 
- Replaced placeholder content in /price-feeds/pro/how-lazer-works.mdx with detailed technical documentation from /lazer/how-lazer-works.mdx
- Updated all references from 'Pyth Lazer' to 'Pyth Pro' to align with product rebrand
- Removed /pages/lazer folder as content has been migrated
- Existing redirects in next.config.js will handle any legacy /lazer/* URLs

Co-Authored-By: aditya@dourolabs.xyz <aditya@dourolabs.xyz>
@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

devin-ai-integration Bot commented Oct 28, 2025

Prompt hidden (unlisted session)

@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

devin-ai-integration Bot commented Oct 28, 2025

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@vercel
Copy link
Copy Markdown

vercel Bot commented Oct 28, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Oct 28, 2025 5:39pm
documentation Building Building Preview Oct 28, 2025 5:39pm

@aditya520 aditya520 merged commit 344cd91 into main Oct 28, 2025
4 of 5 checks passed
@aditya520 aditya520 deleted the devin/1761672971-move-lazer-docs-to-pro branch October 28, 2025 17:48
@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

devin-ai-integration Bot commented Oct 28, 2025

Vercel Deployment Status

I've investigated the failing "Vercel – documentation" check and wanted to provide context:

What I've verified:

  • ✅ Local build passes: npm run build completes successfully with no errors
  • ✅ All GitHub Actions checks pass: pre-commit, test
  • ✅ Primary Vercel deployment succeeds: "Vercel – docs" (pyth-network/docs) deployed successfully with working preview at https://docs-git-devin-1761672971-move-lazer-docs-to-pro-pyth-network.vercel.app
  • ❌ Secondary Vercel deployment fails: "Vercel – documentation" (pyth-stuff/documentation)

Analysis:
Since the code builds locally and the primary "docs" deployment succeeded, this appears to be a configuration issue with the "pyth-stuff/documentation" Vercel project rather than a code problem. The two Vercel projects may have diverged in their settings (Node version, build commands, environment variables, root directory, etc.).

Questions for maintainers:

  1. Is the "pyth-stuff/documentation" Vercel project still intended to be active, or is it a legacy project?
  2. If it's intended to stay active, could someone with Vercel access compare its configuration with the working "pyth-network/docs" project and align the settings?
  3. If it's legacy, should we consider disabling/detaching its GitHub integration to prevent it from blocking PRs?

I don't have access to the Vercel deployment logs to see the specific error, but I'm happy to help investigate further if someone can share the logs or grant access.

Note: The page /price-feeds/pro/how-lazer-works builds correctly (verified in local build output), and the existing redirects in next.config.js will handle any legacy /lazer/* URLs properly.

@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

devin-ai-integration Bot commented Oct 28, 2025

Preview of the updated page:

You can view the migrated "How Pyth Pro Works" page at:
https://docs-git-devin-1761672971-move-lazer-docs-to-pro-pyth-network.vercel.app/price-feeds/pro/how-lazer-works

This shows the full technical documentation that was previously in the /lazer folder, now updated with "Pyth Pro" branding.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

1 more reviewer

@aditya520 aditya520 aditya520 approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@aditya520